-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix regression caused by registry-proxy #4805
Conversation
Hi @kumarom. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kumarom The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Can one of the admins verify this patch? |
743c64f
to
55cd455
Compare
This PR addresses kubernetes#4604 by adding a new selector to concerned svc/rc only. This also reverts `kubernetes.io/minikube-addons` to `registy` for registry-proxy so that addon manager can deploy registry-proxy when registry addon is enabled.
55cd455
to
d76d874
Compare
Thank you for fixing this! |
This PR addresses #4604 by adding a new selector to concerned svc/rc only.
This also reverts
kubernetes.io/minikube-addons
toregisty
for registry-proxyso that addon manager can deploy registry-proxy when registry addon is enabled.